Security sentinel robot

ABSTRACT

A building monitoring system includes a first sensor configured to detect a first condition in the space, a second sensor configured to detect a second condition in the space, and a robotic sentinel. The robotic sentinel includes a memory for storing one or more rules each configured to identify an alert condition for the space based on the first and/or second conditions in the space, a communications module configured to communicate with a remote device over a network, and a controller operatively coupled to the sensors, the memory, and the communications module. The controller is configured to apply the one or more rules to the first and second detected conditions in the space to identify one or more alert conditions and determine what action is required by the robotic sentinel, and if action is required, command the robotic sentinel to travel to a location of the alert condition.

TECHNICAL FIELD

The disclosure generally relates to building monitoring systems, andmore particularly to systems and methods for monitoring conditions in abuilding.

BACKGROUND

Building Automation Systems (BAS) and/or various home control systemsare used to control one of more functions of a building or home. ABuilding Automation System and/or a home control system can include, forexample, an HVAC system, a lighting control system, a fire suppressionsystems, a security system, and/or any other suitable buildingautomation system. A Building Automation System and/or home controlsystems typically include one or more sensors and/or other devices thatare operatively coupled to a central controller or the like, often viawireless communication. These sensors and/or devices may be used tomonitor parameters within the building or home, including, but notlimited to, temperature, humidity, motion, etc.

What would be desirable are improved methods and systems for enhancedbuilding security and data collection.

SUMMARY

This disclosure generally relates to systems and method for enhancedbuilding security and data collection.

In a first example, a method for monitoring a condition in or nearbuilding, wherein the building includes one or more sensors eachdetecting a sensed condition, may comprise storing two or more rules.Each rule may define a rule defined event that is detectable via one ormore of the sensed conditions sensed by the one or more of sensors and arecommended action to take in response to the corresponding rule definedevent. The method may further comprise monitoring the one or more sensedconditions of the one or more sensors over time and repeatedly applyingthe two or more rules to the one or more sensed conditions of the one ormore sensors to identify a rule defined event of the two or more rules.The recommended action may include deploying a robotic sentinel to alocation at or near the sensor having the sensed condition which matchedthe rule defined event.

Alternatively or additionally to any of the examples above, in anotherexample, the rule defined event for at least one rule may comprise atemperature outside of a predetermined range.

Alternatively or additionally to any of the examples above, in anotherexample, the rule defined event for at least one rule may comprise anactivated motion detector during a predefined time period.

Alternatively or additionally to any of the examples above, in anotherexample, the rule defined event for at least one rule may comprise ahumidity outside of a predetermined range.

Alternatively or additionally to any of the examples above, in anotherexample, the rule defined event for at least one rule may comprise anactivated fire alarm.

Alternatively or additionally to any of the examples above, in anotherexample, the rule defined event for at least one rule may comprise anactivated gas detector.

Alternatively or additionally to any of the examples above, in anotherexample, the rule defined event for at least one rule may comprise anactivated leak detector.

Alternatively or additionally to any of the examples above, in anotherexample, when the robotic sentinel arrives at the location at or nearthe sensor or device which matched the rule defined event, the roboticsentinel may poll the sensor or device for updated data.

Alternatively or additionally to any of the examples above, in anotherexample, if the updated data of the sensor or device matches the ruledefined event, a camera on the robotic sentinel may be activated.

Alternatively or additionally to any of the examples above, in anotherexample, the method may further comprise transmitting a video feed fromthe robotic sentinel to a remote device over a network.

Alternatively or additionally to any of the examples above, in anotherexample, the method may further comprise saving the video feed as a datafile.

Alternatively or additionally to any of the examples above, in anotherexample, the recommended action may further comprise delivering an alertto a remote device over a network.

Alternatively or additionally to any of the examples above, in anotherexample, the method may further comprise the robotic sentinel may be arobotic vacuum.

In another example, a building monitoring system configured to be usedin a space within a building may comprise a first sensor configured todetect a first condition in the space, a second sensor configured todetect a second condition in the space, and a robotic sentinel. Therobotic sentinel may comprise a memory for storing one or more ruleseach configured to identify an alert condition for the space based onthe first and/or second conditions in the space, a communications moduleconfigured to communicate with a remote device over a network, and acontroller operatively coupled to the first sensor, the second sensor,the memory, and the communications module. The controller may beconfigured to apply the one or more rules to the first and seconddetected conditions in the space to identify one or more alertconditions and determine what, if any, action is required by the roboticsentinel, and if action is required, command the robotic sentinel totravel to a location of the alert condition.

Alternatively or additionally to any of the examples above, in anotherexample, the controller may be further configured to provide an alert tothe remote device via the communications module.

Alternatively or additionally to any of the examples above, in anotherexample, the controller may be configured to activate a camera mountedon the robotic sentinel at the location of the alert condition.

Alternatively or additionally to any of the examples above, in anotherexample, a video feed acquired from the camera may be transmitted to theremote device.

Alternatively or additionally to any of the examples above, in anotherexample, the robotic sentinel may be a robotic vacuum.

In another example, a server for monitoring a space of a building maycomprise a memory for storing two or more rules. Each rule may define arule defined event that is detectable via one or more of sensedconditions in the space and a recommended action to take in response tothe corresponding rule defined event. The server may further comprise aninput/output port for receiving one or more sensed conditions from thespace and a controller operatively coupled memory and the input/outputport. The controller may be configured to monitor the one or more sensedconditions over time, repeatedly applying the two or more rules to theone or more monitored sensed conditions to identify when a rule definedevent of the two or more rules occurs, and perform the recommendedaction defined by the rule that resulted in the rule defined event. Therecommended action may comprise deploying a robotic sentinel within thespace to a location that includes the sensed condition which matches therule defined event.

Alternatively or additionally to any of the examples above, in anotherexample, the one or more sensed conditions may comprise uncomfortable orunsafe conditions, and wherein the rule defined event for a first ruleof the two or more rules may comprise a temperature outside of apredetermined range and a second rule of the two or more rules maycomprise an activated motion detector.

The preceding summary is provided to facilitate an understanding of someof the features of the present disclosure and is not intended to be afull description. A full appreciation of the disclosure can be gained bytaking the entire specification, claims, drawings, and abstract as awhole.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure may be more completely understood in consideration of thefollowing detailed description of various embodiments in connection withthe accompanying drawings, in which:

FIG. 1 is a schematic view of an illustrative building including varioushome automation systems;

FIG. 2 is a schematic block diagram of an illustrative home or buildingautomation system in communication with illustrative external devicesand networks;

FIG. 3 is a schematic block diagram of first and second illustrativecontrollers;

FIG. 4 is a schematic block diagram of a plurality of controllers incommunication with an external server;

FIG. 5 is schematic block diagram of a security sentinel system;

FIG. 6 is a flow chart of an illustrative method for data collection anddetermining if alert condition is present;

FIG. 7 is an illustrative sensor database;

FIG. 8 is an illustrative system rules database;

FIG. 9 is flow chart of an illustrative method for retrieving data fromthe security sentinel an illustrative; and

FIG. 10 is flow chart of an illustrative method for operating the userdevice base module.

While the disclosure is amenable to various modifications andalternative forms, specifics thereof have been shown by way of examplein the drawings and will be described in detail. It should beunderstood, however, that the intention is not to limit aspects of thedisclosure to the particular embodiments described. On the contrary, theintention is to cover all modifications, equivalents, and alternativesfalling within the spirit and scope of the disclosure.

DESCRIPTION

The following detailed description should be read with reference to thedrawings in which similar elements in different drawings are numberedthe same. The detailed description and the drawings, which are notnecessarily to scale, depict illustrative embodiments and are notintended to limit the scope of the disclosure. The illustrativeembodiments depicted are intended only as exemplary. Selected featuresof any illustrative embodiment may be incorporated into an additionalembodiment unless clearly stated to the contrary.

This disclosure generally relates to building and/or home automationsystems, and more particularly to enhanced security and data collectionthroughout the building and/or home automation system. For clarity, thefollowing description will be described with respect to a homeautomation system including a comfort system (e.g., an HVAC system), asecurity system, and/or any number of Internet of Things (IoT) devices(e.g., household devices having built-in wireless connectivity,sometimes called “smart” devices or “connected” devices), however thesystems and methods described herein may be applied to commercialbuildings, hotels, apartment buildings, etc. The home automation systemmay include one or more of an HVAC system, a lighting control system, afire suppression system, a security system, and any other suitable homeautomation system devices.

FIG. 1 is a schematic view of a building 2 having an illustrativeheating, ventilation, and air conditioning (HVAC) system 4 and anillustrative security system 14. The building 2 may be routinelyoccupied by a person or people 3 and, in some cases, one or more pets 5.While FIG. 1 shows a typical forced air type HVAC system, other types ofHVAC systems are contemplated including, but not limited to, boilersystems, radiant heating systems, electric heating systems, coolingsystems, heat pump systems, and/or any other suitable type of HVACsystem, as desired. The illustrative HVAC system 4 of FIG. 1 includesone or more HVAC components 6 a, 6 b (collectively, 6), a system ofductwork and air vents including a supply air duct 8 and a return airduct 20, and one or more controllers 22. The one or more HVAC components6 may include, but are not limited to, a furnace, a heat pump, anelectric heat pump, a geothermal heat pump, an electric heating unit, anair conditioning unit, a humidifier, a dehumidifier, an air exchanger,an air cleaner, a damper, a valve, and/or the like.

The illustrative HVAC system 4 may further include one or more sensorsor devices 10 a, 10 b (collectively, 10) configured to measure aparameter of the environment to be controlled. The one or more sensorsor devices 10 may include, but are not limited to, temperatures sensors,humidity sensors, carbon dioxide sensors, occupancy sensors, proximitysensors, etc. Each of the sensor/devices 10 may be operatively connectedto the controller 22 via a corresponding communications port (notexplicitly shown). It is contemplated that the communications port maybe wired and/or wireless. When the communications port is wireless, thecommunications port may include a wireless transceiver, and thecontroller 22 may include a compatible wireless transceiver. It iscontemplated that the wireless transceivers may communicate using astandard and/or a proprietary communication protocol. Suitable standardwireless protocols may include, for example, cellular communication,ZigBee, Bluetooth, WiFi, IrDA, dedicated short range communication(DSRC), EnOcean, or any other suitable wireless protocols, as desired.

It is contemplated that the controller(s) 22 may be configured tocontrol the comfort level in the building or structure by activating anddeactivating the HVAC component(s) 6 in a controlled manner. Thecontroller(s) 22 may be configured to control the HVAC component(s) 6via a wired or wireless communication link 24. In some cases, thecontroller(s) 22 may be a thermostat, such as, for example, a wallmountable thermostat, but this is not required in all embodiments. Sucha thermostat may include (e.g. within the thermostat housing) or haveaccess to a temperature sensor for sensing an ambient temperature at ornear the thermostat. In some instances, the controller(s) 22 may be azone controller, or may include multiple zone controllers eachmonitoring and/or controlling the comfort level within a particular zonein the building or other structure. As will be described in more detailherein, the controller(s) 22 may be configured to control the securitysystem and/or other home automation devices or to communicate withseparate controllers dedicated to the security system and/or other homeautomation devices.

In the illustrative HVAC system 4 shown in FIG. 1 , the HVACcomponent(s) 6 may provide heated air (and/or cooled air) via theductwork throughout the building 2. While not explicitly shown, the HVACcomponent(s) 6 may be in fluid communication with every room and/or zonein the building 2 via the ductwork 8 and 20, but this is not required.In operation, when a heat call signal is provided by the controller(s)22, an HVAC component 6 a (e.g., forced warm air furnace) may beactivated to supply heated air to one or more rooms and/or zones withinthe building 2 via supply air ducts 8. The heated air may be forcedthrough supply air duct 8 by a blower or fan 17. In this example, thecooler air from each zone may be returned to the HVAC component 6 (e.g.forced warm air furnace) for heating via return air ducts 20. Similarly,when a cool call signal is provided by the controller(s) 22, an HVACcomponent 6 b (e.g. air conditioning unit) may be activated to supplycooled air to one or more rooms and/or zones within the building orother structure via supply air ducts 8. The cooled air may be forcedthrough supply air duct 8 by the blower or fan 17. In this example, thewarmer air from each zone may be returned to the HVAC component 6 b(e.g., air conditioning unit) for cooling via return air ducts 20. Insome cases, the HVAC system 4 may include an internet gateway or otherdevice 26 that may allow one or more of the HVAC components, asdescribed herein, to communicate over a wide area network (WAN) such as,for example, the Internet.

In some cases, the system of vents or ductwork 8 and/or 20 can includeone or more dampers (not explicitly shown) to regulate the flow of air,but this is not required. For example, one or more dampers may becoupled to one or more controller(s) 22, and can be coordinated with theoperation of one or more HVAC components 6. The one or morecontroller(s) 22 may actuate dampers to an open position, a closedposition, and/or a partially open position to modulate the flow of airfrom the one or more HVAC components 6 to an appropriate room and/orzone in the building or other structure. The dampers may be particularlyuseful in zoned HVAC systems, and may be used to control which zone(s)receives conditioned air from the HVAC component(s) 6.

In many instances, one or more air filters 28 may be used to remove dustand other pollutants from the air inside the building 2. In theillustrative example shown in FIG. 1 , the air filter(s) 30 is installedin the return air duct 20, and may filter the air prior to the airentering the HVAC component 6, but it is contemplated that any othersuitable location for the air filter(s) 30 may be used. The presence ofthe air filter(s) 28 may not only improve the indoor air quality, butmay also protect the HVAC components 6 from dust and other particulatematter that would otherwise be permitted to enter the HVAC component.

In some cases, and as shown in FIG. 1 , the illustrative HVAC system 4may include an equipment interface module (EIM) 30. When provided, theequipment interface module 30 may, in addition to controlling the HVACunder the direction of the thermostat, be configured to measure ordetect a change in a given parameter between the return air side and thedischarge air side of the HVAC system 4. For example, the equipmentinterface module 30 may measure a difference in temperature, flow rate,pressure, or a combination of any one of these parameters between thereturn air side and the discharge air side of the HVAC system 4. In somecases, the equipment interface module 30 may be adapted to measure thedifference or change in temperature (delta T) between a return air sideand discharge air side of the HVAC system 4 for the heating and/orcooling mode. The delta T for the heating and cooling modes may becalculated by subtracting the return air temperature from the dischargeair temperature (e.g. delta T=discharge air temperature−return airtemperature)

In some cases, the equipment interface module 30 may include a firsttemperature sensor 32 a located in the return (incoming) air duct 20,and a second temperature sensor 32 b located in the discharge (outgoingor supply) air duct 8. Alternatively, or in addition, the equipmentinterface module 34 may include a differential pressure sensor includinga first pressure tap 34 a located in the return (incoming) air duct 20,and a second pressure tap 34 b located downstream of the air filter 28to measure a change in a parameter related to the amount of flowrestriction through the air filter 28. In some cases, the equipmentinterface module 30, when provided, may include at least one flow sensorthat is capable of providing a measure that is related to the amount ofair flow restriction through the air filter 28. In some cases, theequipment interface module 34 may include an air filter monitor. Theseare just some examples.

When provided, the equipment interface module 30 may be configured tocommunicate with the controller 22 via, for example, a wired or wirelesscommunication link 36. In other cases, the equipment interface module 30may be incorporated or combined with the HVAC controller 22. In eithercase, the equipment interface module 30 may communicate, relay orotherwise transmit data regarding the selected parameter (e.g.temperature, pressure, flow rate, etc.) to the controller 22. In somecases, the controller 22 may use the data from the equipment interfacemodule 30 to evaluate the system's operation and/or performance. Forexample, the controller 22 may compare data related to the difference intemperature (delta T) between the return air side and the discharge airside of the HVAC system 4 to a previously determined delta T limitstored in the controller 22 to determine a current operating performanceof the HVAC system 4.

The illustrative security system 14 may include a central controller 38and a number of sensors/devices 12 a, 12 b, 12 c (collectively, 12).While the security system controller 38 is illustrated as a separatecontroller from the HVAC controller 22, it is contemplated that thesecurity system controller 38 and the HVAC controller 22 may be providedas a single controller which communicates with and controls both theHVAC system 4 and the security system 14. The sensor/devices 12 may beconfigured to detect threats within and/or around the building 2. Insome cases, some of the sensor/devices 12 may be constructed to detectdifferent threats. For example, some of the sensor/devices 12 may belimit switches located on doors and windows of the building 2, which areactivated by entry of an intruder into the building 2 through the doorsand windows. Other suitable security sensor/devices 12 may include fire,smoke, water, carbon monoxide, and/or natural gas detectors, to name afew. Still other suitable security system sensor/devices 12 may includemotion sensors that detect motion of intruders in the building 2 ornoise sensors or microphones that detect the sound of breaking glass. Itis contemplated that the motion sensor may be passive infrared (PIR)motion sensors, a microwave motion sensor, an ultrasonic motion sensor,a tomographic motion sensor, a video camera having motion detectionsoftware, a vibrational motion sensor, etc. In some cases, one or moreof the sensor/devices 12 may include a video camera. In some cases, thesensor/devices 12 may include a horn or alarm, a damper actuatorcontroller (e.g. that closes a damper during a fire event), a lightcontroller for automatically turning on/off lights to simulateoccupancy, and/or any other suitable device/sensor. These are justexamples. More generally, the sensor/devices 12 may be any type ofsensor or device suitable for operation in a building automation system.

During operation of the illustrative security system 14, the centralcontroller 38 monitors the status of each of the sensor/devices 12. Upondetecting a change of status in one of the sensor/devices 12, thecentral controller may activate an alarm device, record and/or transmitlive video from one of the sensor/devices 12, operate an actuator,contact an off-site central monitoring station (not shown), and/orperform any other suitable action.

Each of the sensor/devices 12 may be operatively connected to thecentral controller 38 via a corresponding communications port (notexplicitly shown). It is contemplated that the communications port maybe wired and/or wireless. When the communications port is wireless, thecommunications port may include a wireless transceiver, and the centralcontroller 38 may include a compatible wireless transceiver. It iscontemplated that the wireless transceivers may communicate using astandard and/or a proprietary communication protocol. Suitable standardwireless protocols may include, for example, cellular communication,ZigBee, Bluetooth, WiFi, IrDA, dedicated short range communication(DSRC), EnOcean, or any other suitable wireless protocols, as desired.

The building 2 may be further provided with additional network connectedor “smart” devices (e.g., WiFi enabled), also known as Internet ofThings (IoT) devices. These devices may include lighting 40, homeappliances 18 (such as, but not limited to, robotic vacuums, coffeepots, etc.), water heaters 16, voice activated smart speakers (e.g.,AMAZON ECHO™ or GOOGLE HOME™), WiFi enabled power outlets, garage dooropeners, door locks, televisions, speakers, doorbells, water valves,video cameras, wearable devices, etc. Other devices in the building 2may include, but are not limited to, a radiofrequency receiver, athermal imager, a radar device, a lidar device, an ultrasound device,etc. It is contemplated that the additional network connected devicesmay be in communication with or configured to communicate or interfacewith the HVAC controller 22 and/or the central security controller 38.In some instances, the additional network connected devices may have oneor more individual controllers which in turn communicate with the HVACcontroller and/or the security controller 38.

FIG. 2 is a schematic view of a home automation system 50 thatfacilitates remote access to, control of, and/or external communicationto/from the HVAC system 4, the security system 14, and/or other homeautomation devices 16, 18, 40 shown in FIG. 1 . The home automationsystem 50 may be considered a building control system or part of abuilding control system. The illustrative home automation system 50includes an HVAC controller, for example, controller 22 (see FIG. 1 ),that is configured to communicate with and control one or more HVACcomponents 6 of the HVAC system 4 and a security system controller 38(see FIG. 1 ) that is configured to communicate with and control one ormore security sensors and/or devices 12. As discussed above, thecontrollers 22, 38 may be provided as separate and discrete controlunits or combined into a single control unit, as desired. Further, whilenot explicitly shown, the smart home devices and sensors 16, 18, 40 maycommunicate with control programs or controllers which in turncommunicate with the HVAC controller 22 and/or security systemcontroller 38. Alternatively, the smart home devices and sensors 16, 18,40 may be configured to communicate directly with the HVAC controller 22and/or security system controller 38.

The HVAC controller 22 may communicate with the one or more HVACcomponents 6 of the HVAC system 4 via a wired or wireless link 24 andwith the smart home devices and sensors 16, 18, 40 (and/or the controlprograms thereof) via a wired or wireless link 70. Similarly, thesecurity system controller 38 may communicate with one or more securitysensors and/or devices 12 via a wired or wireless link 68 and with thesmart home devices and sensors 16, 18, 40 (and/or the control programsthereof) via a wired or wireless link 72. If provided separately, it isnot required for both the HVAC controller 22 and the security systemcontroller 38 to be in communication with the smart home devices andsensors 16, 18, 40 (and/or the control programs thereof). For example,the HVAC controller 22 and the security system controller 38 may be incommunication with one another via a wired or wireless link 74 such thatinformation may be passed between the HVAC controller 22 and thesecurity system controller 38.

Additionally, the controllers 22, 38 may communicate over one or morewired or wireless networks that may accommodate remote access and/orcontrol of the controllers 22, 38 via another device 52 such as a smartphone, tablet, e-reader, laptop computer, personal computer, key fob, orthe like . As shown in FIG. 2 , the HVAC controller 22 may include afirst communications port 54 for communicating over a first network 56,and in some cases, a second communications port 58 for communicatingover a second network 60. Similarly, the security system controller 38may include a first communications port 62 for communicating over thefirst network 56, and in some cases, a second communications port 64 forcommunicating over the second network 60. In some cases, the firstnetwork 56 may be a wireless local area network (LAN), and the secondnetwork 60 (when provided) may be a wide area network or global network(WAN) including, for example, the Internet. In some cases, the wirelesslocal area network 56 may provide a wireless access point and/or anetwork host device that is separate from the controllers 22, 38. Inother cases, the wireless local area network 56 may provide a wirelessaccess point and/or a network host device that is part of at least oneof the controller 22, 38. In some cases, the wireless local area network56 may include a local domain name server (DNS), but this is notrequired for all embodiments. In some cases, the wireless local areanetwork 56 may be an ad-hoc wireless network, but this is not required.

In some cases, the controllers 22, 38 may be programmed to communicateover the second network 60 with an external web service hosted by one ormore external web servers 66. A non-limiting example of such an externalweb service is Honeywell's LCBS Connect™ web service. The controllers22, 38 may be configured to upload selected data via the second network60 to the external web service 66 where it may be collected, stored,and/or analyzed on the external web server 66. In some cases, the datamay be indicative of the performance of the HVAC system 4, the securitysystem 14, and/or the smart home devices and sensors 16, 18, 40. Inother cases, the data may be indicative of building activity or lackthereof. Additionally, the controllers 22, 38 may be configured toreceive and/or download selected data, settings, and/or servicessometimes including software updates from the external web service overthe second network 60. The data, settings and/or services may bereceived automatically from the web service, downloaded periodically inaccordance with a control algorithm, and/or downloaded in response to auser request. In some cases, for example, the HVAC controller 22 may beconfigured to receive and/or download an HVAC operating schedule andoperating parameter settings such as, for example, temperature setpoints, humidity set points, start times, end times, schedules, windowfrost protection settings, and/or the like from the web server 66 overthe second network 60. In some instances, the controllers 22, 38 may beconfigured to receive one or more user profiles having at least oneoperational parameter setting that is selected by and reflective of auser's preferences. In still other instances, the controllers 22, 38 maybe configured to receive and/or download firmware and/or hardwareupdates such as, for example, device drivers from the web server 66 overthe second network 60. Additionally, the controllers 22, 38 may beconfigured to receive local weather data, weather alerts and/orwarnings, major stock index ticker data, and/or news headlines over thesecond network 60. These are just some examples.

Depending upon the application and/or where the home automation user islocated, remote access and/or control of the controllers 22, 38 may beprovided over the first network 56 and/or the second network 60. Avariety of remote wireless devices 52 may be used to access and/orcontrol the controllers 22, 38 from a remote location (e.g. remote fromthe controllers 22, 38) over the first network 56 and/or second network60 including, but not limited to, mobile phones including smart phones,tablet computers, laptop or personal computers, wireless network-enabledkey fobs, e-readers, and/or the like. In many cases, the remote wirelessdevices 52 are configured to communicate wirelessly over the firstnetwork 56 and/or second network 60 with the controllers 22, 38 via oneor more wireless communication protocols including, but not limited to,cellular communication, ZigBee, REDLINK™, Bluetooth, WiFi, IrDA,dedicated short range communication (DSRC), EnOcean, and/or any othersuitable common or proprietary wireless protocol, as desired.

In some cases, one or more application program codes (i.e., apps) storedin the memory of the remote device 52 may be used to remotely accessand/or control the controllers 22, 38. Similarly, an application programcode (app) may be used to remotely access and/or control the smart homedevices and sensors 16, 18, 40. The application program code (app) maybe provided for downloading from an external web service, such as theweb service hosted by the external web server 66 (e.g., Honeywell's LCBSConnect™ web service) or another external web service (e.g., ITUNES® orGoogle Play). In some cases, the app may provide a remote user interfacefor interacting with the controllers 22, 38 and/or smart home devicesand sensors 16, 18, 40 at the user's remote device 52. For example,through the user interface provided by the app(s), a user may be able tochange the operating schedule and operating parameter settings such as,for example, temperature set points, humidity set points, start times,end times, schedules, window frost protection settings, accept softwareupdates and/or the like. Additionally, through the user interfaceprovided by the app(s) the user may be able to arm and/or disarm thesecurity system 14, view sensor status, view live or previously capturedvideos or still images and/or the like. Further, through the userinterface provided by the app(s) the user may be able to view the statusof the smart home devices and sensors 16, 18, 40, change a state of thesmart home devices and sensors 16, 18, 40 (e.g., turn on/off), change acontrol parameter (e.g., a water heater temperature set point), and/orthe like.

Communications may be routed from the user's remote device 52 to the webserver 66 and then, from the web server 66 to the appropriate controller22, 38. In some cases, communications may flow in the opposite directionsuch as, for example, when a user interacts directly with thecontrollers 22, 38 to change an operating parameter setting such as, forexample, a schedule change or a set point change, or an association of asecurity system sensor 12 with an arming mode, etc. The change made atthe appropriate controller 22, 38 may then be routed to the web server66 and then from the web server 66 to the remote device 52 where it mayreflected by the application program(s) executed by the remote device52. In some cases, one or both controllers 22, 38 may be used to changean operating parameter in the smart home devices and sensors 16, 18, 40.

In other cases, a user may be able to interact with the controllers 22,38 via a user interface provided by one or more web pages served up bythe web server 66. The user may interact with the one or more web pagesusing a variety of interne capable devices to effect a change at thecontrollers 22, 38 as well as view usage data and energy consumptiondate related to the usage of the HVAC system 4, security events orstatus related to the security system 12, and/or information regardingthe smart home devices and sensors. In still yet another case,communication may occur between the user's remote device 52 and thecontrollers 22, 38 without being relayed through a server. These arejust some examples.

FIG. 3 is an illustrative schematic block diagram of the HVAC controller22 in communication with the security system controller 38 of FIG. 2 .As discussed above with reference to FIG. 2 , the HVAC controller 22and/or the security system controller 38 may be accessed and/orcontrolled from a remote location over the first network 56 and/or thesecond network 60 using a remote wireless device 52 such as, forexample, a smart phone, a tablet computer, a laptop or personalcomputer, a wireless network-enabled key fob, an e-reader, and/or thelike. In some instances, the HVAC controller 22 may be a thermostat, butthis is not required. As shown in FIG. 3 , the HVAC controller 22 andthe security system controller 38 may each include a communicationsblock 76, 77 having a first communications port 54, 62 for communicatingover a first network (e.g., a wireless LAN) and a second communicationsport 58, 64 for communicating over a second network (e.g., a WAN or theInternet). The first communications port 54, 62 can be a wirelesscommunications port including a wireless transceiver for wirelesslysending and/or receiving signals over a first wireless network 56.Similarly, the second communications port 58, 64 may be a wirelesscommunications port including a wireless transceiver for sending and/orreceiving signals over a second wireless network 60. In some cases, thesecond communications port 58, 64 may be in communication with a wiredor wireless router or gateway for connecting to the second network, butthis is not required. In some cases, the router or gateway may beintegral to (e.g., within) the HVAC controller 22 and/or the securitysystem controller 38 or may be provided as a separate device.Additionally, the illustrative HVAC controller 22 and the securitysystem controller 38 may each include a processor (e.g., microprocessor,microcontroller, etc.) 78, 79 and a memory 80, 81. The HVAC controller22 and the security system controller 38 may each also include a userinterface 82, 83, but this is not required. In some cases, only one ofthe HVAC controller 22 or the security system controller 38 may beprovided with a user interface 82, 83. In some cases, one or both of theHVAC controller 22 and the security system controller 38 may include atimer (not shown). The timer may be integral to the processor 78, 79 ormay be provided as a separate component. The respective memory 80, 81 ofthe illustrative HVAC controller 22 and the security system controller38 may be in communication with the respective processor 78, 79. Thememory 80, 81 may be used to store any desired information, such as theaforementioned control algorithm, set points, schedule times, diagnosticlimits such as, for example, differential pressure limits, delta Tlimits, security system arming modes, and the like. The memory 80, 81may be any suitable type of storage device including, but not limitedto, RAM, ROM, EPROM, flash memory, a hard drive, and/or the like. Insome cases, the processor 78, 79 may store information within the memory80, 81, and may subsequently retrieve the stored information from thememory 80, 81.

In many cases, the HVAC controller 22 may include an input/output block(I/O block) 84 having a number of wire terminals (e.g. 86 a-86 d) forreceiving one or more signals from the HVAC system 4 and/or forproviding one or more control signals to the HVAC system 4. For example,the I/O block 84 may communicate with one or more HVAC components 6 ofthe HVAC system 4. The HVAC controller 22 may have any number of wireterminals for accepting a connection from one or more HVAC components 6of the HVAC system 4. However, how many wire terminals are utilized andwhich terminals are wired is dependent upon the particular configurationof the HVAC system 4. Different HVAC systems 4 having different HVACcomponents and/or type of HVAC components 6 may have different wiringconfigurations. As such, an I/O block 84 having four wire terminals, asshown in FIG. 3 , is just one example and is not intended to belimiting. In some cases, the I/O block 84 may be configured to receivewireless signals from one or more HVAC components 6 or sensors 10.

Alternatively, or in addition to, the I/O block 84 may communicate withanother controller, which is in communication with one or more HVACcomponents of the HVAC system 4, such as a zone control panel in a zonedHVAC system, equipment interface module (EIM) (e.g. EIM 34 shown in FIG.1 ) or any other suitable building control device. It is furthercontemplated that the I/O block 84 may communicate with anothercontroller which controls a separate building control system, such as,but not limited to the security system controller 38.

Similarly, the security system controller 38 may include an input/outputblock (I/O block) 85 having a number of wire terminals (e.g. 87 a-87 d)for receiving one or more signals from the security system 12 and/or forproviding one or more control signals to the security system 12. Forexample, the I/O block 85 may communicate with one or more sensors 12 ofthe security system 14. The security system controller 38 may have anynumber of wire terminals for accepting a connection from one or moresensors 12 of the security system 14. However, how many wire terminalsare utilized and which terminals are wired is dependent upon theparticular configuration of the security system 14. As such, an I/Oblock 85 having four wire terminals, as shown in FIG. 3 , is just oneexample and is not intended to be limiting. In some cases, the I/O block85 may be configured to receive wireless signals from one or moresecurity sensors 12. Alternatively, or in addition to, the I/O block 85may communicate with another controller, which is in communication withone or more controllers which controls a separate building controlsystem, such as, but not limited to the HVAC controller 22.

In some cases, a power-transformation block 88, 89 may be connected toone or more wires of the I/O block 84, 85, and may be configured tobleed or steal energy from the one or more wires of the I/O block 84,85. The power bled off of the one or more wires of the I/O block may bestored in an energy storage device 90, 91 that may be used to at leastpartially power the HVAC controller 22 or the security system controller38. In some cases, the energy storage device 90, 91 may be capacitor ora rechargeable battery. In addition, the HVAC controller 22 and/or thesecurity system controller 38 may also include a back-up source ofenergy such as, for example, a battery that may be used to supplementpower supplied to the HVAC controller 22 or the security systemcontroller 38 when the amount of available power stored by the energystorage device 90, 91 is less than optimal or is insufficient to powercertain applications. Certain applications or functions performed by theHVAC controller 22 or the security system controller 38 may require agreater amount of energy than others. If there is an insufficient amountof energy stored in the energy storage device 90, 91, then, in somecases, certain applications and/or functions may be prohibited by theprocessor 78, 79.

The HVAC controller 22 may also include one or more sensors such as forexample, a temperature sensor, a humidity sensor, an occupancy sensor, aproximity sensor, and/or the like. In some cases, the HVAC controller 22may include an internal temperature sensor 92, as shown FIG. 3 , butthis is not required. The HVAC controller 22 may also communicate withone or more remote temperature sensors, humidity sensors, and/oroccupancy sensors 10 located throughout the building or structure.Additionally, the HVAC controller may communicate with a temperaturesensor and/or humidity sensor located outside of the building orstructure for sensing an outdoor temperature and/or humidity if desired.

In some cases, the HVAC controller 22 may include a sensor 94 that isconfigured to determine if a user is in proximity to the buildingcontroller. Similarly, the security system controller 38 may include asensor 95 that is configured to determine if a user is in proximity tothe security system controller 38. In some cases, the sensor 94, 95 maybe a motion sensor or a proximity sensor such as, for example, a passiveinfrared (PIR) sensor. In certain cases in which the sensor 94, 95 is amotion sensor or a proximity sensor, the sensor 94, 95 may be locatedremotely from the HVAC controller 22 and/or the security systemcontroller 38 and may be in wireless communication with the HVACcontroller 22 and/or the security system controller 38 via one of thecommunication ports.

In yet another example, the sensor 94, 95 may be configured to determinethat the user is in proximity to or is expected to be in proximity tothe HVAC controller 22 and/or the security system controller 38 upondetecting that the user's remote device 52 is connected to thebuilding's wireless network which, in some cases, may be the samenetwork to which the HVAC controller 22 and/or the security systemcontroller 38 is also connected. Such functionality is shown anddescribed in U.S. Patent Publication No. 2014/0031989 entitled “HVACCONTROLLER WITH WIRELESS NETWORK BASED OCCUPANCY DETECTION AND CONTROL”,the entirety of which is incorporated by reference herein for allpurposes.

In still other cases, the user's remote device 52 may be configured todetermine that a user is in proximity to the HVAC controller 22 and/orthe security system controller 38 upon sensing a user's interaction withthe HVAC controller 22 and/or the security system controller 38 via theuser interface provided at the HVAC controller 22 and/or the securitysystem controller 38. For example, the sensor 94, 95 may be configuredto sense when the screen of the user interface 82, 83 is touched and/orwhen a button provided at the user interface 82, 83 is pressed by auser. In some cases, the sensor 94, 95 may be a touch sensitive regionprovided on the user interface 82, 83 when the user interface 82, 83incorporates a touch screen display. In other cases, the sensor 94, 95may be associated with a hard button or soft key that is providedseparate from a display of the user interface 82, 83.

In some cases, upon detecting or determining that a user is in proximityto the HVAC controller 22 and/or the security system controller 38 , thesensor 94,95 may deliver a signal to the processor 78, 79 indicatingthat the user is in proximity to the HVAC controller 22 or the securitysystem controller 38. In other cases, upon detecting or determining thata user is in proximity to the HVAC controller 22 or the security systemcontroller 38, the sensor 94, 95 may be configured to transmit a signalto a remote server 66 over a second network 60 via the communicationsblock 76, 77.

The user interface 82, 83, when provided, may be any suitable userinterface that permits the HVAC controller 22 or the security systemcontroller 38 to display and/or solicit information, as well as acceptone or more user interactions with the HVAC controller 22 or thesecurity system controller 38. For example, the user interface 82, 83may permit a user to locally enter data such as temperature set points,humidity set points, starting times, ending times, schedule times,diagnostic limits, responses to alerts, associate sensors to alarmingmodes, and the like. In one example, the user interface 82, 83 may be aphysical user interface that is accessible at the HVAC controller 22 orthe security system controller 38, and may include a display and/or adistinct keypad. The display may be any suitable display. In someinstances, a display may include or may be a liquid crystal display(LCD), and in some cases an e-ink display, fixed segment display, or adot matrix LCD display. In other cases, the user interface 82, 83 may bea touch screen LCD panel that functions as both display and keypad. Thetouch screen LCD panel may be adapted to solicit values for a number ofoperating parameters and/or to receive such values, but this is notrequired. In still other cases, the user interface 82, 83 may be adynamic graphical user interface.

In some instances, the user interface 82, 83 need not be physicallyaccessible to a user at the HVAC controller 22 or the security systemcontroller 38. Instead, the user interface 82, 83 may be a virtual userinterface 82, 83 that is accessible via the first network 56 and/orsecond network 60 using a mobile wireless device such as one of thoseremote devices 52 previously described herein. In some cases, thevirtual user interface 82, 83 may be provided by an app or apps executedby a user's remote device for the purposes of remotely interacting withthe HVAC controller 22 or the security system controller 38. Through thevirtual user interface 82, 83 provided by the app on the user's remotedevice 52, the user may change temperature set points, humidity setpoints, starting times, ending times, schedule times, diagnostic limits,respond to alerts, update their user profile, view energy usage data,arm or disarm the security system, configured the alarm system, and/orthe like. In some instances, changes made to the HVAC controller 22 orthe security system controller 38 via a user interface 82, 83 providedby an app on the user's remote device 52 may be first transmitted to anexternal web server 66. The external web server 66 may receive andaccept the user inputs entered via the virtual user interface 82, 83provided by the app on the user's remote device 52, and associate theuser inputs with a user's account on the external web service. If theuser inputs include any changes to the existing control algorithmincluding any temperature set point changes, humidity set point changes,schedule changes, start and end time changes, window frost protectionsetting changes, operating mode changes, and/or changes to a user'sprofile, the external web server 66 may update the control algorithm, asapplicable, and transmit at least a portion of the updated controlalgorithm over the second network 60 to the HVAC controller 22 or thesecurity system controller 38 where it is received via the second port58, 64 and may be stored in the memory 80, 81 for execution by theprocessor 78, 79. In some cases, the user may observe the effect oftheir inputs at the HVAC controller 22 or the security system controller38.

Rather than a dedicated app, the virtual user interface 82, 83 mayinclude one or more web pages that are transmitted over the secondnetwork 60 (e.g. WAN or the Internet) by an external web server (e.g.web server 66). The one or more web pages forming the virtual userinterface 82, 83 may be hosted by an external web service and associatedwith a user account having one or more user profiles. The external webserver 66 may receive and accept user inputs entered via the virtualuser interface and associate the user inputs with a user's account onthe external web service. If the user inputs include changes to theexisting control algorithm including any temperature set point changes,humidity set point changes, schedule changes, start and end timechanges, window frost protection setting changes, operating modechanges, and/or changes to a user's profile, the external web server 66may update the control algorithm, as applicable, and transmit at least aportion of the updated control algorithm over the second network 60 tothe HVAC controller 22 or the security system controller 38 where it isreceived via the second port 58, 64 and may be stored in the memory 80,81 for execution by the processor 78, 79. In some cases, the user mayobserve the effect of their inputs at the HVAC controller 22 or thesecurity system controller 38.

In some cases, a user may use either the user interface 82, 83 providedat the HVAC controller 22 or the security system controller 38 and/or avirtual user interface 82, 83 as described herein. The two types of userinterfaces 82, 83 that may be used to interact with the HVAC controller22 or the security system controller 38 are not mutually exclusive ofone another. However, in some cases, a virtual user interface 82, 83 mayprovide more advanced capabilities to the user. It is furthercontemplated that a same virtual user interface 82, 83 for both the HVACcontroller 22 and the security system controller 38. Further, asdescribed above, the HVAC controller 22 and the security systemcontroller 38 may be formed as a single controller configured to performthe functions of both the HVAC controller 22 and the security systemcontroller 38 from a single device.

FIG. 4 is a schematic diagram of a plurality of buildings 100 a, 100 b,100 c, 100 n (collectively, 100) each having one or more HVACcontrollers 22 a-n and/or security system controllers 38 a-n incommunication with an external web server 102, such as the external webserver 66 described herein. It is contemplated that devices from anynumber of buildings 100 may be providing information to the externalserver 102. In some cases, hundreds, thousands, tens of thousands, ormore buildings may be in communication with the external web server 102.The buildings 100 a-n may each have one or more of: an HVAC system 104a-n, a security system 106 a-n, or a smart home device, appliance, orsensor 108 a-n such as any of those described above with respect to FIG.1 . The HVAC system 104 a-n, security system 106 a-n, and/or smart homedevices 108 a-n may be in communication with the HVAC controller 22 a-n,security system controller 38 a-n, a combined HVAC and securitycontroller, or other controller configured to operate the systems anddevices within the respective building 102 a-n. The controllers 22 a-n,38 a-n from each building may then relay performance data, operatingparameters, alarm conditions, gas and/or electricity usage, etc. to theexternal server 102. In some cases, the data may be relayed through aWAN to the external server 102. In some cases, the external server 102may be configured to aggregate the data obtained from the individualbuildings 100. As will be described in more detail herein, onceaggregated, the data can be analyzed for trends, to identify outliers,to improve algorithms, etc.

It is contemplated that the HVAC sensors 10, security system sensors 12,and/or smart home devices and sensors 16, 18, 40 may be utilized with asecurity sentinel system to enhance home security and data collection.Generally, the security sentinel may provide sensor feedback toconnected devices in the home (or building) such as thermostats,humidifiers, motion sensors, etc. and may also become a signal boosterfor Wi-Fi in the home. The security sentinel may also respond to alertsfrom connected home devices by traveling to a location inside the homewhere the alert originated and collecting more sensor data, activating acamera, and allowing the user to view the situation in real-time orproviding a report back to the user if they are unable to view a videostream.

FIG. 5 is a block diagram of an illustrative security system 200including a robot security sentinel 202. In some embodiments, thesecurity sentinel 202 may be a robotic vacuum or other mobile internetconnected device positioned within a building or residence. The securitysentinel 202 may be configured to maneuver throughout a building orresidence including various connected sensors 210 such as sensors andother IoT devices that collect data and/or may receive data. While thesecurity sentinel 202 is docked or located at a home location within thebuilding and while the security sentinel 202 moves through the building,a data collection module 204 may receive data from the sensors anddevices 210 in the building and store said data in a first or sensordatabase 206. It is contemplated that the data collection module 204 maybe in direct communication with the sensors and devices 210 via suitablestandard wireless protocols which may include, for example, cellularcommunication, ZigBee, Bluetooth, WiFi, IrDA, dedicated short rangecommunication (DSRC), EnOcean, or any other suitable wireless protocols.In other embodiments, the communication may pass through an intermediaryserver or cloud network 232, but this is not required. In some cases,the data collection module 204 may be a controller similar in form andfunction to the controllers 22, 38 described above and include the sameor similar components and capabilities.

The sensors and connected devices 210 may be a part of a buildingautomation system and may include components of an HVAC system (e.g.,including, but not limited to, a thermostat 212, temperature sensors214, humidity sensors 216, etc.), a lighting control system (e.g.,including, but not limited to, network connected lights 218), a firesuppression system (e.g., including, but not limited to, fire alarms220, smoke detectors, sprinkler systems, etc.), a security system 222(e.g., including, but not limited to, motion sensors, limit switches,noise sensors, cameras etc.), or other internet enabled or “smart”devices (e.g., including, but not limited to indoor air quality (IAQ)monitors 224, carbon dioxide or carbon monoxide sensors 226, leakdetection sensors 228, motion sensors 230, etc.). Any of the sensor ordevices may be a part of or linked to other portions of the buildingautomation system. For example, in some cases, the carbon dioxide orcarbon monoxide sensors 226 may be a part of the HVAC system, althoughthis is not required. The sensors 206 may be any type of sensor, device(including IoT devices), or detectable event suitable for operation inor use within a building automation system. Other sensors or devices 210may include, but are not limited to, occupancy sensors, proximitysensors, microphones, video cameras, still image cameras, a horn oralarm, fire, smoke, water, carbon monoxide, and/or natural gasdetectors, a damper actuator controller (e.g., that closes a damperduring a fire event), a light controller, smart light bulbs, homeappliances such as, but not limited to, robotic vacuums, coffee pots,etc., water heaters, voice activated smart speakers (e.g., AMAZON ECHO™or GOOGLE HOME™), WiFi enabled power outlets, garage door openers, doorlocks, televisions, speakers, doorbells, water valves, video cameras,wearable devices, radiofrequency receivers, thermal imagers, radardevices, lidar devices , ultrasound devices, etc.

The security sentinel 202 may further include a sensor database 206which contains the sensor data (e.g., sensed condition) received fromthe one or more connected devices or sensors 210 in the home orbuilding. For example, a memory accessible by a processor of the datacollection module 204 may be configured to store the database 206 ofsensor data such that historical and current sensor data is readilyaccessible. The security sentinel 202 may maintain a second, or rules,database 234 including a set of rules or algorithms that may be used toidentify certain conditions within or near the building or residence andto determine if a recommendation should be made to a user, if thesecurity sentinel 202, and/or if other sensors or devices 210 should beactivated, as will be described in more detail herein. For example, amotion sensor 230 may detect motion in part of the house where motion isunexpected for a given time period. In response to the motion sensor 230indicating a rule condition has been met, the security sentinel 202 maybe activated and maneuvered to the location of the motion sensor 230 forfurther investigation and data gathering. The security sentinel 202 maybe activated and maneuvered without user intervention.

A set of rules may include at least one rule, two or more rules, threeor more rules, etc. Each rule may define one or more events that includeone or more detectable conditions that when present may be indicative ofan alert condition. The one or more detectable or sensed condition areindicative of a condition of the space in which the security sentinel202 is located and may be data available from any of, but not limitedto, the sensors 210 described herein. The space may be interior to ahome or exterior to the home, as desired. The alert condition may beindicative of an undesirable condition in the home (e.g., too hot or toocold), an unsafe condition in the home (e.g., presence of carbonmonoxide or smoke), of an intruder or unexpected person in the home,etc. An alert condition does not necessarily an urgent or a distresssituation. Rather, an alert condition is one that initiates furtheractions taken by various components of the security system 200. A memoryaccessible by the processor of the data collection module 204 may beconfigured to store the rules database 234 such that the rules andalgorithms are readily accessible.

In some embodiments, the security sentinel 202 may also include a rulesmodule 236. In some embodiments, the rules module 236 may be a separatecontroller and/or processor from the data collection module 204,although this is not required. In other embodiments, the rules module236 may be a part of the data collection module 204. In yet otherembodiments, the rules module 236 and the data collection module 204 maybe components of a security sentinel 202 system controller (notexplicitly shown). In yet further embodiments, the rules modules 236, orthe processing of sensor data and comparison of the data to the rulesdatabase 234 may be performed in the cloud 232 or otherwise remote fromthe security sentinel 202. The rules module 236 may be configured tocompare the data in the sensor database 206 to the rules database 234and determine if there is any sensor data outside of a threshold definedby the rule. If there is sensor data outside of the predefinedthreshold, the rules module 236 may flag the sensor or device 210. Insome cases, the rules module 236 may be configured to command thesecurity sentinel 202 to travel to the location of the flagged sensor ordevice 210 where the security sentinel 202 may collect more data fromthe flagged sensor or device 210 to compare to the rules datable 234. Insome cases, the rules module 236 may be configured to notify the user ofthe flagged sensor or device 210. If the newly collected sensor dataremains outside of the predefined threshold, the rules module 236 may beconfigured to notify the user, active additional sensors or devices,and/or activate other components (e.g., a still or video camera 238) ofthe security sentinel 202.

When the rules database 234 indicated that the user should be notified,an alert or notification may be sent to the user via a remote userdevice 254. The remote device 254 may be any internet connected deviceincluding a smart phone, tablet, e-reader, laptop computer, personalcomputer, etc. Once the notification has been received at the basemodule (e.g., an app or other program) 268, the notification may bedisplayed on a user interface 266 of the device 254. In some cases, anaudio alert (e.g., a beep or chime) or a haptic alert (e.g., avibration) may accompany the notification to alert the user of thenotification.

In some embodiments, the rules database 234 may be downloaded onto thesecurity sentinel 202 located within the residence from an externalserver(s) over a network. The network may be a wide area network orglobal network (WAN), such as the internet. The external server(s) maybe a suite of hardware and software which may sometimes be referred toas “the cloud” 232. In some cases, the communication may pass through anintermediary server or cloud network 232, but this is not required. Insome cases, the cloud 232 may provide the ability for communicationamongst the security sentinel 202, the external server(s), the homesystem 258, the connected sensors or devices 210, and/or one or moreremote devices 254. If so provided, the external server(s) may beconnected to a single building having a security system 200 or theexternal server(s) may be connected to a plurality of security systemsas described with respect to FIG. 4 . The external server(s) may collectand store data from the various devices and sensors 210 from the one ormore connected security systems 202. In other embodiments, the rulesdatabase 234 may be generated locally using a user interface of acontroller of the home system 258, a user interface of the securitysentinel 202 (if so provided, a remote device (e.g., user device 254), aweb client, etc.

The security sentinel 202 may further include a navigation system 240.The navigation system 240 may be configured to map a room using infraredsensors and provide the ability for the security sentinel 202 to movethroughout one or more rooms or living spaces without issue. When thesecurity sentinel 202 is a robotic vacuum, the security sentinel 202 mayalso include a vacuum cleaner 242 which is an electrical apparatus thatcollects dust and small particles from the floors and other surfaces bymeans of suction. The vacuum cleaner 242 may also include rotatingbrushes and/or other features configured to help collect dust and smallparticles.

The security sentinel 202 may be further provided with additionaldevices and system configured to enhance the security of the home orbuilding and/or increase the usability of the security sentinel 202. Forexample, the security sentinel 202 may also include a microphone 244,which an instrument for converting sound waves into electrical energyvariations, which may then be amplified, transmitted, or recorded. Insome embodiments, the microphone 244 may be activated when the rulesmodule 236 deploys the security sentinel 202 to a flagged sensor ordevice 210. The microphone 244 may be used to listen for unexpectednoises from a mechanical device which may indicate a problem with thedevice or to listen for sounds or voices from an unexpected person.These are just some examples. The security sentinel 202 may also includea speaker 246 which is an electroacoustic device, often housed in acabinet and that is connected as a component in an audio system, itsfunction being to make speech or music audible. In some embodiments, thespeaker 246 may be activated to allow a user to communicate with anotherperson (or pet) in the home or building. Additionally, or alternatively,the speaker 246 may be configured to emit prerecorded messages or otheraudio alerts to notify occupants of the home of a detected condition(e.g., fire, intruder, etc.). The security sentinel 202 may also includea still camera and/or a video camera 238 configured to record still ormoving images. In some embodiments, the camera 238 may be configuredtransmit live images or video to a user. Additionally, or alternatively,the camera 238 may be configured to capture and record images or videoin a memory of the camera 238 and/or a memory of the security sentinel202 for later access.

The security sentinel 202 may also include communication channels 248which provide the ability for the security sentinel 202 to communicatewith other devices by way of suitable standard wireless protocols mayinclude, for example, cellular communication, ZigBee, Bluetooth, WiFi,IrDA, dedicated short range communication (DSRC), EnOcean, or any othersuitable wireless protocols. The communications channels 248 may be apart of the data collection module 204, rules modules 236 and/or acontroller of the security sentinel 202, as desired. The securitysentinel 202 may also be provided with a Wi-Fi booster or extender 256configured to extend the coverage of the local Wi-Fi network. Thebooster 256 may work by receiving the existing Wi-Fi signal, amplifyingit and then transmitting the boosted signal.

In some embodiments, the security sentinel 202 may be provided withvoice control 250 which allows the user to send verbal commands to thesecurity sentinel 202 (e.g., which may be received via the microphone244). The voice control 250 may include the control logic necessary toprocess the voice commands. Alternatively, or additionally, the securitysentinel 202 may include a remote control 252 which provides the userthe ability to control the security sentinel 202 remotely. In somecases, the remote control 252 may be a separate and dedicated deviceconfigured to communicate specifically with the security sentinel 202(e.g., as in a television remote). Alternatively, or additionally, theremote control 252 may be a user device 254 including one or moreapplication program codes (i.e., apps) configured to communicate withand/or control the security sentinel 202, as will be described in moredetail herein.

The security system 200 may further include a home system 258. The homesystem 258 may be a security system or other platform for controllingand/or communicating with the connected sensors or devices 210 in thehome. For example, the home system 258 may include a controllerconfigured to execute a control program for a security system (e.g.,arming/disarming) and/or a control program for an HVAC system. In somecases, the home system 258 may act as an intermediary between thesecurity sentinel 202 and the user, although this is not required. Forexample, in some embodiments, the home system 258 may be configured tostore a collection of all of the data from the sensors and device 210,for example, in a home system database 260, to report the data back tothe user. The home system 258 may further include a data retrievalmodule 262 which may connect to the security sentinel 202 to receive thecollected data and stores the data in the home system database. If thesecurity sentinel 202 has recorded video, the data retrieval module 262may be configured to store the video data in the video database 264. Thedata retrieval module 262 may be provided as a part of or separate froma controller configured to issue operating commands to the home systemdevices 210.

FIG. 6 illustrates a flow chart 300 of an illustrative method for datacollection and determining if alert condition is present and if furtheraction should be taken. To begin, the data collection module 204 of thesecurity sentinel 202 is connected to the home system 258, as shown atblock 302. The data collection module 204 may be configured toautomatically scan the local area network and automatically connect withthe home system 258. In other embodiments, user intervention via a userinterface (of the security sentinel 202 and/or the home system 258) aremote device 254, and/or a web client may be required to connect thedata collection module 204 to the home system 258. Once the datacollection module 204 is connected to the home system 258, the datacollection module 204 connects to the available sensors and devices 210,as shown at block 304. In some cases, the home system 258 may act as anintermediary to facilitate connecting the data collection module 204with the available sensors and devices 210. Once communication has beenestablished between the data collection module 204 and the availablesensors and devices 210 (either directly or indirectly via the homesystem 258), the data collection module 204 may send a request to thesensors and devices for data, as shown at block 306. In response to therequest, the data collection module 204 then receives data from theconnected devices 210, as shown at block 308. The data collection module204 then stores the data in the sensor database 206, as shown at block310.

Referring briefly to FIG. 7 , which illustrates an example sensordatabase 400, the sensor database 400 may record additional informationbeyond the measured or perceived parameter. While the database 400 isreferred to as a “sensor” database, the database 400 may also includedata obtained from other IoT devices that do not include sensors. Thesensor database 400 may record the date 402 and the time 404 the datawas obtained. The sensor database 400 may also record the sensor nameand/or type of sensor 406 and the sensor location 408. This may allowdifferent rules to be applied to specific sensors 210. The sensordatabase 400 also records the actual data 410 received from the sensor210. The data may be binary (e.g., on/off, yes/no, enter/exit, etc.), anumerical value, or other data, as desired. In some cases, a length oftime a reading is valid may also be recorded. While not explicitlyshown, the sensor database 400 may record a system identification. Thesystem identification may tie the data to a particular security sentinel202 or security system 200 such that data can be aggregated with othersystems having similar household demographics.

Returning to FIG. 6 , after the data has been stored, or substantiallysimultaneously therewith, the data collection module 204 sends the datato the home system 258 where it is stored in the home system database260, as shown at block 312. After the data has been sent, orsubstantially simultaneously therewith, the data collection module 204may initiate the rules module 236, as shown at block 314. The rulesmodule 236 then compares the sensor database 206 with the rules database234, as shown at block 316. It is contemplated that the storage ofinformation and the processing thereof may be performed within thesecurity sentinel 202, within a dedicated module 236 in the securitysentinel 202, or remotely from the security sentinel 202, as desired.This may be performed at predefined time intervals or in response to aparticular sensor reading, or other triggering event. As the sensordatabase 206 is compared to the rules database 234, the rules module 236may determine if the data exceeds a threshold for a correspondingpredetermined rule, as shown at block 318. If the sensor data does notexceed a predetermined threshold, the process returns to block 306 wherethe data collection module 204 sends a request for sensor data. In otherwords, the rules will be repeatedly applied to the collected data toidentify when a rule defined event occurs. If the sensor data exceeds athreshold, an alert condition is triggered and the sensor location isextracted from the sensor database 206, as shown at block 320. Thesecurity sentinel 202 is then directed to move towards the sensorlocation which triggered the alert condition, as shown at block 322. Ifthe security sentinel 202 is already mobile, the direction of travel maybe rerouted to the sensor location which triggered the alert condition.

Once the security sentinel 202 arrived at the sensor location, the datacollection module 204 collects additional data from the triggeringsensor, as shown at block 324. The rules module 236 then compares thisnewly acquired sensor data to the rules database, as shown at block 326.As the sensor database 206 is compared to the rules database 234, therules module 236 may determine if the data exceeds a threshold for acorresponding predetermined rule, as shown at block 328. If the sensordata does not exceed a predetermined threshold, the process returns toblock 306 where the data collection module 204 sends a request forsensor data. If the newly acquired sensor data also exceeds a threshold,the camera 238 on the security sentinel 202 is activated, as shown atblock 330. The security sentinel 202 may then establish a connection tothe user device 254, as shown at block 332. Once the connection has beenestablished, the security sentinel 202 may send a notification to theuser device 254, as shown at block 334. The notification may includeinformation regarding which sensor triggered the notification and thecorresponding data. The notification may further allow the user toaccept or decline the notification, as shown at block 336. If the userdeclines or otherwise does not accept the notification, the securitysentinel 202 records video data of the sensor location, as shown atblock 338. This video may then be sent to the video database 264 in thehome system 258, as shown at block 340, where the user may access it ata later time. In some cases, the security sentinel 202 may record videofor a predetermined length of the time. It is contemplated that thelength of time video is recorded may vary depending on the triggeringsensor. The process then returns to block 306 where the data collectionmodule 204 sends a request for sensor data.

If the user accepts the notification, the video data may be sent to theuser device 254, as shown at block 342. The video data may be sent inreal time or near to real time to allow the user to view the conditionswhich triggered the alert condition. For example, if a leak detector hasdetected a leak (such as, but not limited to, a water leak), the usermay be able to view the extent of the leak and determine if immediatecorrective action is required. This is just one example of someinformation that may gleaned from a video stream. It is contemplatedthat the security sentinel 202 may transmit the video data for apredetermined length of the time (which may be variable) or until theuser terminates the transmission, as desired. Control is then returnedto the data collection module 204, as shown at block 344 and the processthen returns to block 306 where the data collection module 204 sends arequest for sensor data.

FIG. 8 illustrates an example system rules database 500. The rulesdatabase 500 illustrated in FIG. 8 is not intended to provide a completelisting of the events which may result in an alert condition. Instead,the rules database 500 is provided as an example of some rules definingevents that may be generated for increase the security or comfort(and/or prevent damage thereto) of a building. The rules database 500may include a time range 502 for which the rule applies. For example,rules related to the security of a building may be applied only when thebuilding is unoccupied or expected to be unoccupied whereas conditionswhich may result in property damage or hazardous conditions to theoccupants may be continuously monitored. The rules database 500 may alsoinclude the device or sensor name and/or location 704 and a data range506 which is considered acceptable. In some cases, the data range mayinclude a lower limit and an upper limit where the rule defined event isconsidered to occur if the data is below the lower limit or above theupper limit. In other cases, the data range may be a binary range(detected/not detected, activated/deactivated, on/off, etc.). While eachrow of the rules database 500 illustrates a single rule defined event,it is contemplated that two or more sensor readings can be combined intoa single rule, as desired. In some cases, the data from a single devicemeeting a predetermined criteria may be sufficient to generate an alertcondition. In other cases, the combined data from two or more sensors ordevices meeting predetermined criteria may generate an alert condition.Some events that may result in an alert condition may include, but arenot limited to, an indoor temperature outside a predetermined range, anindoor humidity outside a predetermined range, an indoor air qualityoutside a predetermined range, an activated fire alarm, an activatedcarbon dioxide or carbon monoxide detector, an activated security systemsensor, a detected leak, detected motion, etc. It should be understoodthat the above listing of events is not intended to be comprehensive butrather illustrative of some events that can be monitored using asecurity system and/or security sentinel 202.

FIG. 9 illustrates a flow chart 600 of an illustrative method forretrieving data from the security sentinel 202. In some cases, the homesystem 258 may be configured to request data from the security sentinel202 (additionally, or alternatively to the security sentinel 202automatically transmitting said data). The process begins with the dataretrieval module 262 of the home system 258 connecting to the securitysentinel 202, as shown at block 602. The data retrieval module 262receives the sensor database 206 from the security sentinel 202, asshown at block 604. The sensor data is stored in the home systemdatabase 260, as shown at block 606. The home system database 260 mayinclude similar information to the sensor database 206 in the securitysentinel 202. The data retrieval modules 262 may analyze the data todetermine if video data was received from the security sentinel 202, asshown at block 608. If no video data was received, then the processreturns to continuously polling for data from the security sentinel 202until it is received, as shown at block 612. The process then resumeswith the data retrieval module 262 receiving the data, as shown at block604. Returning to block 608, if video data was received, then the videodata is stored in the video database 264.

FIG. 10 illustrates a flow chart 700 of an illustrative method foroperating the user device base module 268. The method or process beginswith the base module 268 connecting to the security sentinel 202, asshown at block 702. The base module 268 may continuously poll for anotification from the security sentinel 202, as shown block 704. In somecases, the base module 268 may poll on a continuous basis or anintermittent basis, as desired. Once the base module 268 receives anotification from the security sentinel 202, as shown at block 706, thebase module 268 may then determine whether the user accepted thenotification, as shown at block 708. If the notification was acceptedthe video data is displayed on the user device user interface 266, asshown at block 710, but if the notification was not accepted the processreturns to polling for notification from the security sentinel 202, asshown at block 704.

The various modules described herein disclosed herein may be implementedor performed with a general purpose processor, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield programmable gate array signal (FPGA) or other programmable logicdevice, discrete gate or transistor logic, discrete hardware components,or any combination thereof designed to perform the functions describedherein. A general purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

Those skilled in the art will recognize that the present disclosure maybe manifested in a variety of forms other than the specific embodimentsdescribed and contemplated herein. Accordingly, departure in form anddetail may be made without departing from the scope and spirit of thepresent disclosure as described in the appended claims.

What is claimed is:
 1. A method for monitoring a condition in or near abuilding, the method comprising: storing two or more rules that define aplurality of role defined events and a plurality of recommended actions,each rule defining: a rule defined event that is detectable via one ormore of a plurality of sensed conditions sensed by one or more thesensors of the building; and a recommended action to take in response tothe corresponding rule defined event; monitoring the plurality of sensedconditions of the one or more sensors over time; repeatedly applying thetwo or more rules to the plurality of sensed conditions to identify asensed condition that matches a particular rule defined event of theplurality of rule defined events defined by the two or more rules; inresponse to identifying that the sensed condition sensed by a sensor ofthe one or more sensors matches the particular rule defined event,dispatching a robotic sentinel to a location in the building associatedwith the sensor to communicate with the sensor and to poll, using directcommunication, the sensor for an updated one or more sensed conditions;and in response to determining that the updated one or more sensedconditions matches the particular rule defined event, outputting anotification indicative of the particular rule defined event.
 2. Themethod of claim 1, wherein the rule defined event for at least one rulecomprises a temperature outside of a predetermined range.
 3. The methodof claim 1, wherein the rule defined event for at least one rulecomprises an activated motion detector during a predefined time period.4. The method of claim 1, wherein the rule defined event for at leastone rule comprises a humidity outside of a predetermined range.
 5. Themethod of claim 1, wherein the rule defined event for at least one rulecomprises an activated fire alarm.
 6. The method of claim 1, wherein therule defined event for at least one rule comprises an activated gasdetector.
 7. The method of claim 1, wherein the rule defined event forat least one rule comprises an activated leak detector.
 8. The method ofclaim 1, further comprising: in response to identifying that the sensedcondition matches the particular rule defined event and that the roboticsentinel has reached the location associated with the sensor, activatinga camera on the robotic sentinel.
 9. The method of claim 8, furthercomprising transmitting a video feed from the robotic sentinel to aremote device over a network.
 10. The method of claim 8, furthercomprising saving the video feed as a data file.
 11. The method of claim1, wherein the recommended action for at least one rule furthercomprises delivering an alert to a remote device over a network.
 12. Themethod of claim 1, wherein the robotic sentinel is a robotic vacuum. 13.A building monitoring system configured to be used in a space within abuilding, the monitoring system comprising: a plurality of sensorsconfigured to detect a plurality of conditions in the space; and arobotic sentinel, comprising: a memory for storing one or more ruleseach configured to identify an alert condition for the space based onone or more of the plurality of conditions in the space; acommunications module configured to communicate with a remote deviceover a network and with each of the plurality of sensors using directcommunication; and a controller operatively coupled to the memory andthe communications module, the controller configured to: apply the oneor more rules to the plurality of conditions in the space to identify aparticular alert condition associated with one or more conditionsdetected by a sensor of the plurality of sensors in response toidentifying the particular alert conditions associated with the one ormore conditions detected by the sensor, command the robotic sentinel totravel to a location in the space associated with the sensor tocommunicate with the sensor and to poll, using direct communication, thesensor for an updated one or more sensed conditions; and in response todetermining that the updated one or more sensed conditions of the sensormatches the particular alert condition, outputting a notificationindicative of the particular alert condition.
 14. The monitoring systemof claim 13, wherein the controller is further configured to provide analert to the remote device via the communications module.
 15. Themonitoring system of claim 13, wherein the controller is configured toactivate a camera mounted on the robotic sentinel when the roboticsentinel is at the location associated with the sensor.
 16. Themonitoring system of claim 15, wherein a video feed acquired from thecamera is transmitted to the remote device.
 17. The monitoring system ofclaim 13, wherein the robotic sentinel is a robotic vacuum.
 18. A serverfor monitoring a space of a building, the server comprising: a memoryfor storing two or more rules, each rule defining: a rule defined eventthat is detectable via one or more of a plurality of sensed conditionsin the space; and a recommended action to take in response to thecorresponding rule defined event; an input/output port for receiving theplurality of sensed conditions from the space; a controller operativelycoupled memory and the input/output port, the controller configured to:monitor the plurality of sensed conditions over time; repeatedlyapplying the two or more rules to the plurality of monitored sensedconditions to identify when a particular rule defined event of the twoor more rules occurs; in response to identifying the occurrence of theparticular rule defined event, dispatching a robotic sentinel to alocation in the space associated with a sensor that senses a sensedcondition that matches the particular rule defined event to communicatewith the sensor and to poll, using direct communication, the sensor foran updated one or more sensed conditions; and in response to determiningthat the updated one or more sensed conditions of the sensor matches theparticular rule defined event, outputting a notification indicative ofthe particular rule defined event.
 19. The server of claim 18, whereinthe plurality of sensed conditions comprises uncomfortable or unsafeconditions, and wherein the rule defined event for a first rule of thetwo or more rules comprises a temperature outside of a predeterminedrange and a second rule of the two or more rules comprises an activatedmotion detector.